chore: merge design-audit remediation to main with CI fixes#790
chore: merge design-audit remediation to main with CI fixes#790BigSimmo wants to merge 9 commits into
Conversation
…ucedMotion placement - Remove reducedMotion from chromium project use block (TypeScript error; contextOptions already sets this globally) - Revert audit-navigation-auth-regressions.test.ts to main markers (PR 781 introduced markers that don't exist in ClinicalDashboard.tsx) - Revert audit-content-services-regressions.test.ts to main expectations (form source data matches Medium/Source-checked, not Unknown/Local-confirmation)
|
This pull request has been ignored for the connected project Preview Branches by Supabase. |
|
Warning Review limit reached
Next review available in: 22 seconds Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (6)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
CI triageCI failed on this PR. Automated classification of the 2 failed job(s):
Compared with main CI run #3107 (cancelled). Classification is evidence routing, not permission to ignore a failure. Exact quarantined Playwright identities remain governed by the flake ledger. |
The design-audit merge rewrote site-map generation, RAG, schema/drift, and dropped the PwaLifecycle import, which broke lint/typecheck/unit CI. Restore those surfaces from main, drop stale duplicate migrations, and remove the services RightRail remount key rejected by audit regressions.
Keep q/focus/run on the home route props and import service navigator metric helpers so the design-audit UI changes typecheck again.
Summary
reducedMotionbelongs incontextOptions) and restores stale regression test expectations that diverged from current source fixtures.Verification
Risk and rollout
Clinical Governance Preflight
Clinical KB Database(sjrfecxgysukkwxsowpy)